Modification risk degree measurement system, modification risk degree measurement method and modification risk degree measurement program

ABSTRACT

A modification risk degree measurement system includes a central processing unit (CPU), a program storage unit, a data storage unit, an input unit performing a control instruction and data input and an output unit performing data output. In the CPU, extracting module, influence range specifying module, influence degree determining module, risk degree calculating module and refactoring module are incorporated. The extracting module performs extraction processing, the influence range specifying module specifies the influence range, the influence degree determining module determines the influence degree, the risk degree calculating module calculates the risk degree from the influence range and the influence degree, and the refactoring module provides assistance in refactoring.

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application is based upon and claims the benefit of priority from the prior Japanese Patent Applications No. P2001-226730, filed on Jul. 26, 2001; the entire contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] This invention relates to a modification risk degree measurement system, a modification risk degree measurement method and a modification risk degree measurement program, which calculate, as a risk degree, the incidence rate of a possible modification result being caused as a side effect of a modification of in a program when this program is modified

[0004] 2. Description of the Related Art

[0005] In a development process of software, the task of modifying a program is inevitable work. Moreover, as one of techniques for modifying the program, a technique called refactoring is present. Refactoring technique is a technique for improving the maintainability and extensibility of the existing program, and aims to modify module configuration, class configuration and the like without modifying a performing function of the existing program and to impart greater stability to the program.

[0006] What is always a problem in the work of modifying a program as described above is a point that, as a result of the modification in many cases, not only a modification result intended by a programmer (object modification result) is derived, but also a subordinate result not intended by the programmer (side effect result) is generated.

[0007] Various techniques have been developed in order to investigate how the side effect result generated in the work of modifying the existing program can be estimated and avoided and determine in which region of the existing program the side effect result will be generated in a case where the side effect result cannot be avoided. For example, in order to investigate the influence relationships of the respective elements in a program on this problem, a technique called “slicing” has been frequently used (See Japanese Patent Laid-Open (Kokai) No.1994-202905, No.1994-175884 and No.1995-134664). “Slicing” refers to a technique for extracting a part calculating functions to be modified and unmodified functions from the existing program by use of dependency relationships and control dependency relationships in the program during modification. Meanwhile, with a view to measuring the relationships between the respective elements of the program, a technique of measuring a cohesion degree has been proposed (See Japanese Patent Laid-Open No. Hei 11 (1999)-224210). The cohesion degree indicates the extent to which function constitutional units of the program, that is, functions, methods and the like, are functionally independent, and indicates the properties of a single constitutional element unit. Quantitative evaluation of this index is broadly divided into seven stages, and the highest stage is called a “functional cohesion degree,” which indicates a program function constitutional unit capable of being provided by a single function. As a weaker cohesion degree, for example, there is a “chronological cohesion degree,” which indicates a function or the like aggregated by initialization processing. The weakest stage is called a “cryptic cohesion degree,” which indicates a program function constitutional unit where two or more unrelated functions are aggregated into one function. If the cohesion degree is used as described above, then the functions of the function and the method are measured, and quality of the program can be shown as an objective numerical value.

[0008] However, with regard to the slicing technique, though modification can be performed so as not to influence unmodified function, there have been incidences of the case where a portion to be modified is influenced by an unmodified portion therefore proper modification cannot be performed. Moreover, the obtained results have only investigated the existence of an influence relationship among the respective elements. And because it has not been possible to measure the influence degree, it has not been possible for the result of slicing to be a judgment criterion for determining a policy regarding modifying the existing program.

[0009] With regard to the technique for measuring a cohesion degree, in the work of modifying the existing program, whether or not the cohesion degree procedures is tight is not directly related to modifies in the program. If the cohesion degree of the procedures is high, whether or not the measurement technique is suitable for the modifying work has not been able to be explained accurately.

[0010] Moreover, the sole solution is not present in the refactoring plan, and there may be multiple refactoring plans, from which a similar effect can be obtained. However, judgments for ranking refactoring plans present in plural as optimal, suitable, unsuitable and the like are not easy. As a result, though effectiveness of the refactoring of the program has been recognized by general users, it has been rare that the refactoring had been actually applied.

[0011] As described above, according to the related art, when the existing program is modified, though it is possible to estimate the side effect results of the program such as the generation of new bugs, caused by the modification, it has been difficult to measure this side effect result as an objective influence degree and to obtain information to serve as an index for flexibly planning the program alterations by use of the measurement values.

[0012] The present invention was made in consideration of the above-described problems. An object of the present invention is to provide a modification risk degree measurement system, a modification risk degree measurement method and a modification risk degree measurement program, which are capable of measuring influence degrees and influence ranges for the respective plural modification plans, calculating risk degrees from the information of this measurement, and using the risk degrees as indices when the optimal modification plan is selected from among the modification plans present in plural and to provide a modification risk measurement program.

SUMMARY OF THE INVENTION

[0013] In order to attain the above-described object, a first aspect of the present invention inheres in a modification risk degree measurement system, including: (A) an extracting module configured to extract a program constituent element from an program as an influenced element, the program constituent element being influenced by program modification data; (B) an influenced element storage unit configured to store the influenced element; (C) an influence range specifying module configured to specify an influence range from the influenced element; (D) an influence range storage unit configured to store the influence range; (E) an influence degree determining module configured to determine a degree of influence on the program by the influenced element; (F) an influence degree storage unit configured to store the degree of influence; and (G) a risk degree calculating unit configured to calculate a modification risk degree of the program by using the influence range and the degree of influence.

[0014] According to the modification risk degree measurement system in accordance to the first feature of the present invention, a system for calculating the modification risk degree in consideration of both of the influence degree and the influence range is adopted, and thus it is possible to make risk degree estimation excellent in comparison with a system of considering only one thereof.

[0015] A second aspect of the present invention inheres in a program reconstruction support system for assistance to form a plan for program modification, comprising:(A) an extracting module configured to extract a program constituent element from an program as an influenced element, the program constituent element being influenced by program modification data; (B) an influenced element storage unit configured to store the influenced element; (C) an influence range specifying module configured to specify an influence range from the influenced element; (D) an influence range storage unit configured to store the influence range; (E) an influence degree determining module configured to determine a degree of influence on the program by the influenced element; (F) an influence degree storage unit configured to store the degree of influence; (G) a risk degree calculating module configured to calculate a modification risk degree of the program by using the influence range and the degree of influence; and (H) a refactoring module configured to assist to refactor a plan for program modification by using information which includes risk degree.

[0016] A third aspect of the present invention inheres in a modification risk degree measurement method, including the steps of (A) extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; (B) storing the influenced element; (C) specifying an influence range from the influenced element; (D) storing the influence range; (E) determining a degree of influence on the program by the influenced element; (F) storing the degree of influence; and (G) calculating a modification risk degree of the program caused by the program modification data, by using the influence range and the influence degree.

[0017] A fourth aspect of the present invention inheres in a method for supporting computer program reconstruction, including the steps of: (A) extracting a program constituent element from a program as an influenced element, the program constituent element being influenced by program modification data; (B) storing the influenced element; (C) specifying an influence range from the influenced element; (D) storing the influence range; (E) determining a degree of influence on the program by the influenced element; (F) storing the degree of influence; (G) calculating a modification risk degree of the program caused by the program modification data, by using the influence range and the influence degree; and (H) assisting for refactoring a plan for program modification by using information which includes risk degree.

[0018] A fifth aspect of the present invention inheres a computer readable medium which stored a program for driving and controlling a modification risk degree measurement system for measuring a risk degree by a program modification, the program including: (A) a command for extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; (B) a command for storing the influenced element; (C) a command for specifying an influence range from the influenced element; (D) a command for storing the influence range; (E) a command for determining a degree of influence on the program by the influenced element; (F) a command for storing the degree of influence; and (G)a command for calculating a modification risk degree of the program caused by the program modification data by using the influence range and the influence degree.

[0019] A sixth aspect of the present invention inheres a computer readable medium which stored a program for supporting computer program reconstruction, comprising; (A) instructions for extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; (B) instructions for storing the influenced element; (C) instructions for specifying an influence range from the influenced element; (D) instructions for storing the influence range; (E) instructions for determining a degree of influence on the program by the influenced element; (F) instructions for storing the degree of influence; (G)instructions for calculating a modification risk degree of the program caused by the program modification data by using the influence range and the influence degree; and (H) instructions for assisting to refactor a plan for program modification by using information which includes risk degree.

BRIEF DESCRIPTION OF THE DRAWINGS

[0020]FIG. 1 is a block diagram showing a configuration of a modification risk degree measurement system according to an embodiment of the present invention.

[0021]FIG. 2 is a block diagram schematically showing extracting module according to the embodiment of the present invention.

[0022]FIG. 3 is a block diagram schematically showing an influence range specifying module according to the embodiment of the present invention.

[0023]FIG. 4 is a block diagram schematically showing the influence range specifying module according to the embodiment of the present invention.

[0024]FIG. 5 is a block diagram schematically showing a risk degree calculating module according to the embodiment of the present invention.

[0025]FIG. 6 is a block diagram schematically showing a refactoring module according to the embodiment of the present invention.

[0026]FIG. 7 is a flowchart showing the entire flow of a modification risk degree measurement method according to the embodiment of the present invention.

[0027]FIG. 8 is a flowchart showing an operation flow of steps for extracting an influenced element according to the embodiment of the present invention.

[0028]FIG. 9 is a flowchart showing an operation flow of steps for specifying an influence range according to the embodiment of the present invention.

[0029]FIG. 10 is a flowchart showing an operation flow of steps for judging an influence degree according to the embodiment of the present invention.

[0030]FIG. 11 is a flowchart showing an operation flow of steps for calculating a risk degree according to the embodiment of the present invention.

[0031]FIG. 12 is a flowchart showing an operation flow of steps for executing refactoring according to the embodiment of the present invention.

[0032]FIG. 13 shows model diagrams explaining differences between method units and class units in the influence range.

[0033]FIG. 14 shows model diagrams explaining combinations of the influence ranges and the influence degrees.

[0034]FIG. 15 shows model diagrams explaining combinations of the influence ranges and the influence degrees.

[0035]FIG. 16 is an example of displaying two-dimensional parameters of the influence degree and the influence range.

[0036]FIG. 17 is an example of displaying two-dimensional parameters of the influence degree and the influence range.

[0037]FIG. 18 is one example of a program according to the embodiment of the present invention.

[0038]FIG. 19 is an example in a modification of the program according to the embodiment of the present invention.

[0039]FIG. 20 is an example of a modification in the program according to the embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0040] Various embodiments of the present invention will be described with reference to the accompanying drawings. It is to be noted that the same or similar reference numerals are applied to the same or similar parts and elements throughout the drawings, and the description of the same or similar parts and elements will be omitted or simplified.

[0041] In the following descriptions, numerous specific details are set fourth such as specific signal values, etc. to provide a thorough understanding of the present invention. However, it will be obvious to those skilled in the art that the present invention may be practiced without such specific details.

[0042] In a modification risk degree measurement system according to an embodiment of the present invention, a modification risk degree is calculated in consideration of both an “influence range” as a distribution status of influenced elements in the existing program and a “degree of influence” extended over the entire existing program by the influenced elements (refer to FIGS. 16 and 17). Here, the “risk degree” is a scale obtained by judging to what extent of a range and how much a specified modification plan gives an influence over all. For example, the case of modifying highly independent elements is conceived. Such elements are conceived to have a very low influence degree. However, supposing a case where these elements are extensively used in the program, the risk degree is accordingly elevated. On the contrary, the case of modifying lowly independent elements is conceived. Such elements are conceived to have relatively strong connections with other elements and to be large in terms of the degree of influence. However, if these elements are used only in a few regions of the program, then the risk degree thereof is not elevated very much.

[0043] When calculating the risk degree, it is desirable to quantify or normalize the influence range and the influence degree in advance. However, in the present invention, since only information in a source code is used for quantification for both thereof, it is apparent that values having determined upper limits are adopted. Therefore, appropriate normalization can be achieved by counting occurrence positions and an occurrence frequency to be quantized, or alternatively, by means of a preset calculation formula.

[0044] The “numerical value” is defined as a value subjected to quantization, and “quantization” is defined as counting the occurrence for each occurrence position. Moreover, “normalized value” is defined as a value subjected to the normalization, and “normalization” is defined as accommodation of data in a certain range by a specified conversion. Note that, in the above-described specified conversion, there is an obtainment of a certain value by use of a calculation formula and the like. As one example, a vertical axis is set as the quantized or normalized influence degree, a horizontal axis is set as the quantized or normalized influence range, an origin is set as “min,” and the value is set closer to “max” as it is spaced apart from the origin. For the parameter group, the risk degrees are allocated on several kinds of distribution maps in response to the source code and the modification plan. Furthermore, arbitrary weighting is performed for the influence range and the influence degree, and thus the risk degree calculation in response to the purpose of the modification plan can be performed, and the calculation result can be displayed.

[0045] Here, description will be made for the “influence range” according to the embodiment of the present invention. With regard to the influence range, there is a possibility of causing a disparity between an expansion state when the entire program is seen at a method (function) unit and an expansion state when the entire program is seen at a class (module) unit. A concrete example is shown. In FIG. 13, seen at the method unit, a method m1 is used in nine methods, a method m2 is used in four methods, and therefore, it can be said that the influence range of the method m1 is wider. However, seen at the class unit, the method m1 is used in three classes, classes C, D and E, but the method m2 is used in four classes, classes B, D, E and I. Which taken to be the definition of the influence range is a matter not uniformly determined. For example, in the case of the object-oriented language, since the respective classes are expected to be designed with relatively high independence, it is more reasonable that the influence range is quantified by the number of classes rather than by simply counting the number of methods in many cases. However, in the case of the C language or the like, in some cases, the independency of the respective modules (classes) is not always high, and the quantification in terms of function units is desirable. Specifically, with regard to the “influence range,” flexible unit modification is desirable according to the program modification plan and the programming language used.

[0046] The “influence degree” is obtained from a value counting external variables, arguments, class variables, return values or the like, which are present in the program (source code), or from a normal value obtained by normalizing the counting value. With regard to the influence given to other source codes by the external variables, the arguments, the class variables, the return values or the like, a primary influence directly giving an influence thereto, a secondary influence indirectly receiving an influence therefrom, and the like are conceived. Moreover, the influence degree needs a flexible modification in response to a kind of variables and the programming language for use.

[0047] First, consideration will be made of a point of problem in a system of considering only the influence degree simply. In FIG. 14, it is assumed that influence degrees of two methods, the method m1 and the method m2, are the same. At this time, in the case of calculating risk degrees in consideration only of the influence degrees, since the influence degrees are the same, the risk degrees are calculated as being the same. However, in this case, if a modification according to the method m1 is performed, then there is a possibility that a secondary influence to the other nine elements in the program is derived. Meanwhile, with a modification according to the method m2, there is a possibility that a secondary influence to the other four elements is derived. In this case, obviously, it is not reasonable that the both modification risk degrees are regarded as the same.

[0048] Next, consideration will be made of a point of problem in a system of considering only the influence range. As shown in FIG. 15, any of two methods, the method m1 and the method m2 has a possibility of deriving the secondary influence to the other four elements in the program. If only the influence range is considered, the risk degrees of the modifying task for these two methods are calculated to be the same. However, in this case, it is assumed that there is a difference between the influence degrees of the method m1 and the method m2. In the case where the external variables and number of parameters for use in the method m1 are more than those for use in the method m2, obviously, it is not reasonable that the risk degrees are regarded as the same without considering the difference between the two influence degrees.

[0049] In explanation of the embodiment of the present invention, a modification for a general object-oriented language such as Java and C++ is set as subject matter.

[0050] (Program Modification Risk Degree Measurement System)

[0051] As shown in FIG. 1, a program modification risk degree measurement system according to the embodiment of the present invention embraces a central processing unit (CPU) 20, a program storage unit 21, a data storage unit 22, an input unit 23 performing a control instruction and data input, an output unit 24 performing data output, a host computer 25, an interface 26, a system bus 27, and the like. Through the system bus 27, the CPU 20, a program storage unit 21, a data storage unit 22, an input unit 23, an output unit 24, a host computer 25, and an interface 26 are mutually connected, so as to communicate each other.

[0052] The CPU 20 executes the modification risk degree measurement program stored in the program storage unit 21, so as to realize the processing of the modification risk degree measurement system according to this embodiment. The CPU 20 incorporates modules such as extracting module 1, influence range specifying module 2, influence degree determining module 3, risk degree calculating module 4 and refactoring module 5 therein. The extracting module 1 extracts a program constituent element in the existing program influenced by program modification data as an influenced element from the existing program and the program modification data. The influence range specifying module 2 specifies an influence range from the influenced element. The influence degree determining module 3 determines the degree of influence on the entire existing program of the influenced element. The risk degree calculating module 4 calculates the modification risk degree of the existing program from the program modification data using the influence degree and the influence range. The refactoring module 5 performs assistance when the optimal program modification data is selected based on the calculated risk degree.

[0053] Each of these modules which stored in the program storage unit 21 is a logical functional software, and each thereof can operate on a system physically different from others. The data storage unit 22 includes an influenced element storage unit 8, an influence range storage unit 9, an influence degree storage unit 10, a risk degree storage unit 11, a refactoring storage unit 12, a source code storage unit 6 and a modification plan storage unit 7. The influenced element storage unit 8 stores an execution result of the influenced element extracting program and the like. The influence range storage unit 9 stores an execution result of the influence range specifying program and the like. The influence degree storage unit 10 stores an execution result of the influence degree determining program and the like. The risk degree storage unit 11 stores an execution result of the risk degree calculating program and the like. The refactoring storage unit 12 stores an execution result of the refactoring program and the like. Moreover, the source code storage unit 6 stores a source code inputted from the input unit 23, and the modification plan storage unit 7 stores a modification plan inputted from the input unit 23. The input unit 23 has a keyboard, a mouse and the like provided therein and receives data such as the source code and the modification plan. Note that, besides the above, the input unit 23 may receive data, the input may be performed from the host computer 25 through the interface 26 and a storage device such as a floppy disk. The output unit 24 has a display unit, a printer and the like provided therein and outputs data. Note that, besides the above, the output unit 24 may store an output result in a file or a storage device such as a floppy disk, or may output the data to the host computer 25 through the interface 26.

[0054] As shown in FIG. 2, the extracting module 1 according to the embodiment of the present invention has a parsing unit 11 and an influenced element extracting unit 12. The parsing unit 11 reads modification plans 7 a,7 b,7 c, . . . and source codes 6 a,6 b,6 c, . . . through the input unit 23, performs parsing, and prepares information conceived to be necessary in specifying the influence ranges of a syntactic structure, variable definition and the like. Note that, though not shown, the inputted modification plans 7 a,7 b,7 c, . . . are transmitted to the modification plan storage unit 7 to be stored therein, and the source codes 6 a,6 b,6 c, . . . are transmitted to the source code storage unit 6 to be stored therein. The influenced element extracting unit 12 extract source code regions (influenced element information 8 a,8 b,8 c, . . . ) having a possibility of being modified, which results from execution of the modification plans 7 a,7 b,7 c, . . . by use of the modification plans 7 a,7 b,7 c, . . . and the source codes 6 a,6 b,6 c, . . . analyzed in the parsing unit 11. As an example of the modification plan, finite difference information for use in a patch command of the UNIX is given. Note that the extracted influenced element information 8 a,8 b,8 c, . . . are stored in the influenced element storage unit 8 for each element.

[0055] As shown in FIG. 3, the influence range specifying module 2 according to the embodiment of the present invention has a unit deciding unit 20, a method searching unit 21, a class searching unit 22 and an influence range specifying unit 23. The method deciding unit 20 takes out one of modification plans 7 a,7 b,7 c, . . . stored in the storage unit 7 and one of the influenced element information 8 a,8 b,8 c, . . . stored in the influenced element storage unit 8, and decides units of the influence range by an instruction of an operator or a stored program in response to the purpose of the modification plans 7 a,7 b,7 c, . . . . In this embodiment, two units, the method unit and the class unit, are used. When the method unit is selected in the unit deciding unit 20, the influenced element information 8 a,8 b,8 c, . . . is transmitted to the method searching unit 21. When the class unit is selected, the influenced element information 8 a,8 b,8 c, . . . are transmitted to the class searching unit 22.

[0056] In the method searching unit 21, a method serving as the influenced element information 8 a,8 b,8 c, . . . are searched by use of slicing technique and the like. The searched influenced element information 8 a,8 b,8 c, . . . , are transmitted to the influence range specifying unit 23 per method unit. In the class searching unit 22, a class serving as the influenced element information 8 a,8 b,8 c, . . . are searched by use of an interclass dependency relationship graph and the like. The searched influenced element information 8 a,8 b,8 c, . . . are transmitted to the influence range specifying unit 23 per class unit. The influence range determining unit 23 determines a distribution status of the influenced element information 8 a,8 b,8 c, . . . , for example, in the source codes 6 a,6 b,6 c, . . . per unit. Specifically, an occurrence position and an occurrence count and the like of the influenced element information 8 a,8 b,8 c, . . . are extracted. Note that the extraction of the occurrence position and the occurrence count of the influenced element information 8 a,8 b,8 c, . . . are realized by performing merge processing of the influenced element information 8 a,8 b,8 c, . . . and the source codes 6 a,6 b,6 c, . . . , and the like. Moreover, since the influence range is used later when the risk degree is calculated, the influence range is quantized or normalized. Information such as the occurrence position, the occurrence count and the normalized numerical value and the like of the influenced element information 8 a,8 b,8 c, . . . , which are obtained by the influence range specifying unit 23, are stored in the influence range storage unit 9. Note that, for units of the influence range, ones such as the method unit, the class unit, the block unit, the variable unit are conceived, and any unit is set usable.

[0057] As shown in FIG. 4, the influence degree determining module 3 according to the embodiment of the present invention has an influence degree extracting unit 30 and an influence degree normalizing unit 31. The influence degree determining module 3 takes out one of the influenced element information 8 a,8 b,8 c, . . . stored in the influenced element storage unit 8, and extracts an influence degree contained in the influenced element information 8 a,8 b,8 c, . . . serving as a base of the influence degree. In the influence degree, two kinds of information, dynamic information 18 b and static information 18 c, are present. The dynamic information 18 b indicates the number counted as the influenced element information 8 a,8 b,8 c, . . . by the extracting module 1, the execution count based on an operation profile, and the like. The static information 18 c indicates a reference frequency of the influenced element information 8 a,8 b,8 c, . . . in the program, a mutual dependency relationship between the influenced element information 8 a,8 b,8 c, . . . and the other elements, and the like. Between the extracted influence degrees, the dynamic information 18 b is transmitted to the influence degree normalizing unit 31, and the static information 18 c is transmitted to the influence degree storage unit 10 to be stored therein. In the influence degree normalizing unit 31, the dynamic information is quantized or normalized. Information such as external variables, an argument, a class variable and a return value, which are quantized or normalized as the dynamic information 18 b, is quantized by counting the occurrence count and the like or normalized by use of a calculation formula and the like. Note that the information such as a numerical value obtained by the influence degree normalizing unit 31 is stored as the dynamic information 18 b in the influence degree storage unit 10. The information stored in the influence degree storage unit 10 is accumulated and utilized from now on as secondary information from the outside, which is utilized when the value of the influence degree is adjusted, for example, when the calculation formula for the influence degree is created.

[0058] As shown in FIG. 5, the risk degree calculating module 4 according to the embodiment of the present invention has a risk degree calculating unit 40 and a risk degree display unit 41. The risk degree calculating unit 40 takes out influence range information 9 a,9 b,9 c, . . . stored in the influence range storage unit 9 and the influenced element information 8 a,8 b,8 c, . . . composing a pair with this influence range information 9 a,9 b,9 c, . . . one by one, takes influence degree information 10 a,10 b,10 c, . . . corresponding to the influence range information 9 a,9 b,9 c, . . . out of the influence degree storage unit 10, and calculates the risk degree for each influenced element information 8 a,8 b,8 c, . . . by adding the extracted influence range information 9 a,9 b,9 c, . . . , influenced element information 8 a,8 b,8 c, . . . and influence range information 9 a,9 b,9 c, . . . . Note that, besides the influence range and the influence degree, arbitrary weighting (numerical value assignment) is performed for the calculation formula, and thus it is possible to perform the risk degree calculation in response accordance with various purposes. Note that the information such as the numerical value obtained by the risk degree calculating unit 40 is stored in the risk degree storage unit 11.

[0059] The risk degree display unit 41 edits information such as the numerical value obtained by the risk degree calculating unit 40, and prepares to browse the risk degree information by use of the input unit and the like shown in FIG. 1. Concretely, the influence degree is inputted as a first parameter, the influence range is inputted as a. second parameter, a parameter group expressed two-dimensionally by the first parameter and the second parameter is constituted, and the risk degree is displayed two-dimensionally (refer to FIG. 16 and FIG. 17). As a display method, not only a simple linear combination but also a combination reflecting various policies can be conceived.

[0060] As shown in FIG. 6, the refactoring module 5 according to the embodiment of the present invention is constituted of a refactoring candidate extracting unit 50, a refactoring risk degree calculating unit 52 and a refactoring execution assisting unit 54. The refactoring candidate extracting unit 50 takes out and parses the source codes 6 a,6 b,6 c, . . . inputted to the source code storage unit 6, explores a candidate plan for refactoring, and extracts refactoring candidates 51 a,51 b,51 c, . . . . The extracted refactoring candidates 51 a,51 b,51 c, . . . , are transmitted to the refactoring risk degree calculating unit 52, and temporarily stored in a refactoring storage unit 55.

[0061] The refactoring risk degree calculating unit 52 calculates the refactoring risk degree based on the extracted refactoring candidates 51 a,51 b,51 c, . . . and the source codes 6 a,6 b,6 c, . . . . The refactoring candidates 51 a,51 b,51 c, . . . are added to the calculated risk degree, transmitted as risk degree-added refactoring candidates 53 a,53 b,53 c, . . . to the refactoring execution assisting unit 54, and stored in the refactoring storage unit 55. The refactoring execution assisting unit 54 submits information to be useful for actually refactoring the original source codes 6 a,6 b,6 c, . . . by use of the risk degree-added refactoring candidates 53 a,53 b,53 c, . . . , and performs assistance for the refactoring. Note that the refactoring candidates 51 a,51 b,51 c, . . . , the risk degree-added refactoring candidates 53 a,53 b,53 c, . . . and the refactored source code 55 a are stored in the refactoring storage unit 55.

[0062] (Modification Risk Degree Measurement Method)

[0063] Next, an explanation will be made of the measurement method using the modification risk degree measurement system according to the embodiment of the present invention. With reference to the flowchart shown in FIG. 7, explanation will be made for an operation where the operator inputs the source codes 6 a,6 b,6 c, . . . and the modification plans 7 a,7 b,7 c, . . . , outputs the risk degree, and performs refactoring based on the risk degree.

[0064] (a) In step S101, first, as shown in FIG. 7, the operator inputs the source codes 6 a,6 b,6 c, . . . and the modification plans 7 a,7 b,7 c, . . . . First, an objective source codes 6 a,6 b,6 c, . . . are read out of the input unit 23, and stored in the source code storage unit 6. Next, the modification plans 7 a,7 b,7 c, . . . are read out of the input unit 23, and stored in the modification plan storage unit 7.

[0065] (b) In step S102, the source codes 6 a,6 b,6 c, . . . and the modification plans 7 a,7 b,7 c, . . . , which are stored in step S101, are read out of the source code storage unit 6 and the modification plan storage unit 7 again, these are parsed, information such as the syntactic structure and the variable definition is prepared, and preparation of extraction processing is performed.

[0066] (c) In step S103, the extraction processing of the influenced element information 8 a,8 b,8 c, . . . are performed by use of the extracting module 1. From the modification plans 7 a,7 b,7 c, . . . , the modification elements are taken out one by one, and elements (influenced element information 8 a,8 b,8 c, . . . ) that can be possibly influenced by these elements are extracted from the source codes 6 a,6 b,6 c, . . . . The extracted influenced element information 8 a,8 b,8 c, . . . are transmitted to the influenced element storage unit 8 to be stored therein.

[0067] (d) In step S104, by use of the influence range specifying module 2, the influence range specifying processing of the influenced element information 8 a,8 b,8 c, . . . are performed. The influenced element information 8 a,8 b,8 c, . . . stored in the influenced element storage unit 8 are taken out one by one, the range unit is decided in response to the purpose of the modification plans 7 a,7 b,7 c, . . . , the distribution position of the influenced element information 8 a,8 b,8 c, . . . in the source codes 6 a,6 b,6 c, . . . and the like are determined for each range unit. The determined influence range is transmitted to the influence range storage unit 9 to be stored therein.

[0068] (e) In step S105, by use of the influence degree determining module 3, the influence degree determining processing of the influenced element information 8 a,8 b,8 c, . . . are performed. Out of the modification plans 7 a,7 b,7 c, . . . , the modification elements are taken out one by one, and the influenced element information 8 a,8 b,8 c, . . . corresponding to the modification elements are extracted from the source codes 6 a,6 b,6 c, . . . . The extracted influence degree is transmitted to the influence degree storage unit 10 to be stored therein.

[0069] (f) In step S106, by use of the risk degree calculating module 4, the calculation processing of the risk degree is performed. The value obtained by quantizing or normalizing the influence degree and the value obtained by quantizing or normalizing the influence range are taken out, and the risk degree is calculated by use of the calculation formula and outputted on a screen of a general-purpose machine or the like. Information of the calculated risk degree is transmitted to the risk degree storage unit 11 to be stored therein.

[0070] (g) In step S107, by use of the refactoring module 5, refactoring processing is performed based on the information of the modification risk degree obtained in steps S101 to S106. The source codes 6 a,6 b,6 c, . . . are taken out of the source code storage unit 6, and the refactoring candidates 51 a,51 b,51 c, . . . are extracted. Furthermore, the risk degree is calculated based on the extracted refactoring candidates 51 a,51 b,51 c, . . . , and the refactoring assistance is executed based on the calculated risk degree-added refactoring candidates 53 a,53 b,53 c, . . . . The source code having been subjected to the refactoring assistance is transmitted to the refactoring storage unit 55 to be stored therein.

[0071] In step S102 shown in FIG. 7, the source codes 6 a,6 b,6 c, . . . and the modification plans 7 a,7 b,7 c, . . . , which are stored in step S101, are parsed, each information such as the syntactic structure and the variable definition is prepared, and preparation of the extraction processing is performed. For an algorithm for parsing the syntax and the like, a publicly known technique for use in a compiler and the like is used. This is composed of a code table (variable definition information) and a syntax tree (syntactic structure information). As information registered therein, there are pieces of information such as a variable name, a defined row number, a variable type, an initial value of the variable, a pointer to a high-order (parent) variable information, a pointer to a low-order head (firstborn) variable information, a pointer to a variable (younger brother) having the same parent and defined next, a pointer to information of a variable redefined by the variable, a pointer to a list of the information of the variables redefined by the variable, a list of pointers to regions where the variables are set on the syntax tree, a list of pointers to regions where the variables are referred to on the syntax tree, information of variables in an inclusion relationship with the variables, and the like.

[0072] The syntax tree expresses the syntactic structure of the program by representing a connection of statements obtained in response to the execution order of the program. Each node of the syntax structure corresponds to a command statement or formula of the program and contains information. The entire information constitutes the program. In information owned by the syntax structure, in the case of an assignment statement, as statement class (=assignment) information, there are a row number, a pointer to a basic block, a pointer to a formula of an assignment source, a pointer to a column of a name table corresponding to a variable of an assignment destination, a pointer to the next statement and the like. In the case of a conditional branch statement, as statement class (=conditional branch) information, there are a row number, a pointer to the basic block, a pointer to conditional formula information, a pointer to a statement head of a then portion, a pointer to a statement head of an else portion, a pointer to the next statement, and the like. Moreover, as information of the conditional formula, there are a class of an operator, a pointer to information of a right-hand side formula, a pointer to information of a left-hand side formula, and the like.

[0073] Next, explanation will be made for an operation flow of step S103 (extraction processing of the influenced element information 8 a,8 b,8 c, . . . ) in FIG. 7 with reference to FIG. 8.

[0074] (a) First, in step S201, the source codes 6 a,6 b,6 c, . . . to be extracted are read, and next, in step S202, the modification plans 7 a,7 b,7 c, . . . having the purpose of modifying the source codes 6 a,6 b,6 c, . . . are read. At this time, for one of the source codes 6 a,6 b,6 c, . . . , the modification plans 7 a,7 b,7 c, . . . may be present in plural.

[0075] (b) Next, in step S203, one modification element is taken out of the modification plans 7 a,7 b,7 c, . . . read in step S202, a region (influenced element information 8 a,8 b,8 c, . . . ) that can be possibly influenced by the modification element is searched from the source codes 6 a,6 b,6 c, . . . , and the number of influenced element information 8 a,8 b,8 c, . . . are counted and quantized. Note that a set of the influenced element information 8 a,8 b,8 c, . . . influenced by a specified modification c is defined as:

ε(c)  (1)

[0076] Note that the normalization will be explained in a modification example.

[0077] (c) Next, in step S205, the searched influenced element information 8 a,8 b,8 c, . . . are extracted one by one and stored in the influenced element storage unit 8. Finally, in step S206, a determination is made as to whether or not the modification element currently processed is the last modification element, and if the modification element is not the last modification element, then the process returns to step S203, and the above-described operations are repeated. If the modification element is the last modification element, this extraction processing is terminated.

[0078] Next, with reference to FIG. 9, explanation will be made for an operation flow of step S104 (specifying processing of the influence range) of FIG. 7.

[0079] (a) First, in step S301, the source codes 6 a,6 b,6 c, . . . to be extracted are read, and in step S302, the influenced element information 8 prepared in step S103 is read.

[0080] (b) Next, in step S303, a unit of the influence range itself is decided. This is one, with regard to one influenced element information 8 a,8 b,8 c, . . . taken out in step S303, modifying a unit of partitioning the source codes 6 a,6 b,6 c, . . . in response to the purpose of the modification plans 7 a,7 b,7 c, . . . , the programming language for use or the like, which are executed by the operator or the stored program. In this embodiment, the source codes 6 a,6 b,6 c, . . . are partitioned by the method unit and the class unit. Decided as the method unit, the source codes 6 a,6 b,6 c, . . . are partitioned by the method unit, and decided as the class unit, the source codes 6 a,6 b,6 c, . . . are partitioned by the class unit.

[0081] (c) Next, in step S304, one influenced element information 8 a,8 b,8 c, . . . are taken out of the influenced element information 8. Next, in step S305, the occurrence position and the occurrence count of the influenced element information 8 a,8 b,8 c, . . . in the source codes 6 a,6 b,6 c, . . . are obtained.

[0082] (d) In step S306, the influenced range is specified based on the occurrence position and the occurrence count, and moreover, the influenced range is quantized or normalized. As the influence range, the influence range of a specified modification c is expressed as the number of methods where the elements of the set E(c) of the influenced element information 8 a,8 b,8 c, . . . are present, the occurrence count of the methods is counted and quantized for each occurrence position (method and class), which is defined as:

ρ(c)  (2)

[0083] Note that the normalization will be explained in a modification example.

[0084] (e) Note that the specified influenced range and the quantized or normalized influenced range are stored in the influence range storage unit in step S307.

[0085] (f) Finally, in step S308, a determination is made as to whether or not the influenced element information 8 a,8 b,8 c, . . . currently processed is the last influenced element information 8 a,8 b,8 c, . . . , and if the influenced element information 8 a,8 b,8 c, . . . are not the last influenced element information 8 a,8 b,8 c, . . . , then the process returns to step S304, and the above-described operations are repeated. If the influenced element information 8 a,8 b,8 c, . . . are the last influenced element information 8 a,8 b,8 c, . . . , then this specifying processing is terminated.

[0086] Next, with reference to FIG. 10, explanation will be made for an operation flow of step S105 (determining processing of the influence degree) of FIG. 7.

[0087] (a) First, in step S401, the information of the influenced element information 8 a,8 b,8 c, . . . prepared in step S103 is read, and in step S402, one influenced element information 8 a,8 b,8 c, . . . are taken out of the information of the influenced element information 8 a,8 b,8 c, . . . .

[0088] (b) Next, in step S403, the influence degree of the influenced element information 8 a,8 b,8 c, . . . are determined. In the influence degree, there are two kinds of information, dynamic information and static information. As the dynamic information, there are the number counted as the influenced element information 8 a,8 b,8 c, . . . by the extracting module of the influenced element information 8 a,8 b,8 c, . . . and the execution count based on the operation profile, which concretely indicate the external variable, the argument, the class variable, the return value and the like. As the static information, there are a reference frequency of the influenced element information 8 a,8 b,8 c, . . . in the program, a mutual dependency relationship between the influenced element information 8 a,8 b,8 c, . . . and the other elements, and the like. In this embodiment, between the influence degrees, the dynamic information regarded as important is quantized or normalized, and the static information is transmitted to the influence degree storage unit 10 to be stored therein.

[0089] Here, the influence degree of the dynamic information is quantized or normalized. The influence degree of specific modification to the specific element m (a method and class) is set as a total number of the external variables, the arguments, the class variables and the return values, which are used in a specified element (method and class), and the external variables, the arguments, the class variables and the return values are counted for each occurrence thereof in the method and the class, which are defined:

Δ(m)  (3)

[0090] Note that explanation will be made for the normalization in the modification example.

[0091] (c) In step S404, the determined influence degree and the quantized or normalized influence degree are stored in the influence degree storage unit 10. Finally, in step S405, determination is made as to whether or not the influenced element currently processed is the last influenced element information 8 a,8 b,8 c, . . . , and if the influenced element information 8 a,8 b,8 c, . . . are not the last influenced element information 8 a,8 b,8 c, . . . , the process returns to step S402, and the above-described operations are repeated. If the influenced element information 8 a,8 b,8 c, . . . are the last influenced element information 8 a,8 b,8 c, . . . , this determining processing is terminated.

[0092] Next, with reference to FIG. 11, explanation will be made for an operation flow of step S106 (calculation processing of the risk degree) of FIG. 7. (a) First, in step S501, the influence range information 9 a,9 b,9 c, . . . are read, and one pair of the influenced element information 8 a,8 b,8 c, . . . and the influence range information 9 a,9 b,9 c, . . . are taken out of the influence range information 9 a,9 b,9 c, . . . (S502). Next, in step S503, the influence degree corresponding to the pair of the influenced element information 8 a,8 b,8 c, . . . and the influence range information 9 a,9 b,9 c, . . . are read out of the influence degree storage unit 10.

[0093] (b) Next, in step S504, the risk degree for each influenced element information 8 a,8 b,8 c, . . . are calculated. The risk degree for each influenced element information 8 a,8 b,8 c, . . . are calculated by adding the influence degree and the influence range information 9 a,9 b,9 c, . . . . In calculating the risk degree, in this embodiment, for the specified modification c, a risk degree D(c) is calculated by the following formula using the formula (1), the formula (2) and the formula (3).

D(c)=[(C _(ρ)ρ(c))²+Σ(C _(Δ)Δ(m))²]^(1/2)  (4)

[0094] The second term in the right-hand side is the sum when the variable m as an element of ε(c) is modified. Moreover, C_(ρ) and C_(Δ) are arbitrary coefficients.

[0095] (c) Next, in step S505, a determination is made as to whether or not the currently processed pair of the influenced element information 8 a,8 b,8 c, . . . and the influence range is the last pair, and if the pair is not the last pair, then the process returns to step S502, and the above-described operations are repeated. If the pair is the last pair, the processing exits from the calculation processing.

[0096] (d) Finally, in step S506, the entire modification plans 7 a are overlapped to calculate the risk degree, and the risk degree is displayed. As a display method of the risk degree, explanation will be made for two display examples in this embodiment.

[0097] (1) Display examples for the case where the influence range is narrow though the risk degree is high and the case where the risk degree is low though the influence range is wide

[0098] As shown in FIG. 16, the case where the influence range is narrow though the risk degree is high is represented as a region A, and the case where the risk degree is low though the influence range is wide is represented as a region B. In this case, the risk degrees in the both parameter groups are set to be low.

[0099] (2) Display examples for the case where the way of combination is modified depending on values of the influence range and the influence degree though the way of combining the influence range and the influence degree is not constant

[0100] In the method shown in FIG. 17, the following definitions are made:

[0101] Region A: the risk degree is defined to be 0;

[0102] Region B: the risk degree is defined to be equal to the influence range ρ;

[0103] Region C: the risk degree is defined to be equal to the influence degree Δ;

[0104] Region D: the risk degree is defined to be the maximum values of ρ and Δ; and

[0105] Region E: the risk degree is defined to be 1 (maximum value).

[0106] Note that the above-described risk degree displays may be displayed for each risk degree calculation of the influenced element information 8 a,8 b,8 c, . . . in step S504.

[0107] Next, with reference to FIG. 12, explanation will be made for an operation flow of step S107 (assistance processing of the refactoring) of FIG. 7.

[0108] (a) First, in step S601, the source codes 6 a,6 b,6 c, . . . are read, and in step S602, the refactoring candidates 51 a,51 b,51 c, . . . are explored and extracted. Note that the constitution and procedure for use in step S602 is set similar to the constitution and procedure for use when the modification plans 7 a,7 b,7 c, . . . are prepared, and that the refactoring candidates 51 a,51 b,51 c, . . . are defined to correspond to the modification plans 7 a,7 b,7 c, . . . .

[0109] (b) Next, in step S603, the risk degree of the refactoring candidates 51 a,51 b,51 c, . . . are calculated based on the source codes 6 a,6 b,6 c, . . . and the refactoring candidates 51 a,51 b,51 c, . . . . For calculating the risk degree of the refactoring candidate, the step (S106) and calculation formula for use in the risk degree calculating module 4 is used. When the risk degree of the refactoring candidate is calculated, the risk degree of the refactoring candidate is added to the original source codes 6 a,6 b,6 c, . . . , and the risk degree-added refactoring candidate is prepared.

[0110] (c) In step S604, information for assisting the refactoring execution for the risk degree-added refactoring candidates 53 a,53 b,53 c, . . . prepared in step S603 is prepared, added to the risk degree-added refactoring candidates 53 a,53 b,53 c, . . . , and outputted on the screen of the general-purpose machine. The operator judges the risk degree and reasonability of the refactoring by the outputted assistance information, and executes the refactoring.

[0111] Note that the “assistance” of the refactoring according to the present invention indicates modification contents of the modification plan obtained by parsing the source codes 6 a,6 b,6 c, . . . and the modification plans 7 a,7 b,7 c, . . . , a designation of the influence range and influence degree influenced by the requested modification, a correction instruction of the side effect result caused by the modification, an investigation result of a possibility of correcting the side effect result, a judgment of the reasonability of the requested modification plan and a reason thereof, and the like.

[0112] (How Modification Risk Degree, Method and Program are Uesd)

[0113] Here, explanation will be made for the function of the present invention by use of a concrete example. FIG. 18 shows a Java program converting an inputted formula into the Reverse Polish Notation. Now here, as the modification plans 7 a,7 b,7 c, . . . , the following two are conceived:

[0114] (A) Modification of Error( )

[0115] The displayed message is partially modified (FIG. 19); and

[0116] (B) Modification of isDigit( )

[0117] The determination order of true/false values is modified (FIG. 20).

[0118] Then, these risk degrees are measured.

[0119] First, the modification of error( ) of (A) is considered. The influenced element information 8 a,8 b,8 c, . . . by this modification is only the error( ) itself. Next, when the influence range of this influenced element information 8 a,8 b,8 c, . . . is investigated, it is understood that the influenced element information 8 a,8 b,8 c, . . . are used in two regions, match( ) and term( ), and that the occurrence count is two. Therefore, from the formula (2), the influence range of this modification becomes 2.

[0120] Next, the influence degree of the influenced element information 8 a,8 b,8 c, . . . are quantified. Since the error( ) does not influence the operation of the other elements at all, the influence degree thereof is the minimum. From the formula (3), this influence degree is quantified to be 0. These influence range and influence degree are overlapped to obtain the risk degree. When both values of the arbitrary coefficients C_(ρ) and C_(Δ) are set as 1 and the formula (4) is used, the risk degree becomes 2.

[0121] Next, the modification of isDigit( ) of (B) is considered. The influenced element information 8 a,8 b,8 c, . . . by this modification is the isDigit( ) itself and term( ) utilizing the return value of this method. Next, when the influence range of this influenced element information 8 a,8 b,8 c, . . . is investigated, the isDigit( ) itself is used in the term( ), and the term( ) is used in four regions in expression( ). Since the influenced element information 8 a,8 b,8 c, . . . occur once in the term( ) itself and four times in the expression( ), the influence range of this modification becomes 5 from the formula (2).

[0122] Next, the influence degree of the influenced element information 8 a,8 b,8 c, . . . are quantified. The return value of the isDigit( ) influences the operation of the term( ). Since the variable influencing the operation is 1, from the formula (3), this influence degree is quantified to be 1. These influence range and influence degree are overlapped to obtain the risk degree. When both values of the arbitrary coefficients C_(ρ) and C_(Δ) are set as 1 and the formula (4) is used, the risk degree becomes 6.

[0123] As described above, when the modification of (A) and (B) are compared with each other according to the present invention, it is quantitatively evaluated that the latter one is the modification with higher risk degree.

[0124] (Modification Example)

[0125] In this embodiment of the present invention, the risk degree is calculated in consideration of both of the influence range and the influence degree. However, when seen from the viewpoint that, since only the information in the source code is used for quantification for both of the influence range and the influence degree, it is apparent that values having determined upper limits are taken, normalization of the influence range and the influence degree can be made based on a ratio of how much the method (class) serving as the influenced element is contained in the entire methods (classes) contained in the source program, and the like. Therefore, for the normalization of the influence range in step S306, the following calculation formula may be used.

[0126] In the case of taking the number of methods in which the elements of the set ε(c) of the influenced elements by the specified modification c is present as the influence range,

ρ_(R)(c)=ρ(c)/Elms  (5)

[0127] where Elms is defined as the number of the entire elements in the program.

[0128] Moreover, for the normalization of the influence degree in step S403, the following calculation formula may be also used.

Δ_(R)(m)=(gv(m)+pv(m)+cv(m)+rv(m))/(GV+pv(m)+CV+rv(m))  (6)

[0129] where gv(m) is the number of external variables used by m, pv(m) is the number of arguments of m, cv(m) is the number of class variables used by m, rv(m) is the number of return values of m, GV is the number of the entire external variables, and CV is the number of the entire class variables. Moreover, when GV+pv(m)+CV+rv(m)=0, Δ(m)=0.

[0130] It is also possible to obtain the risk degree by substituting the value normalized by the above-described formula (5) and formula (6) into the formula (4).

[0131] As described above, according to the present invention, for the respective modification plans present in plural, the extent of the influence degree and the size of the influence range are measured quantitatively, risk degrees are calculated from these pieces of information, and refactoring is tested, and thus the risk degrees can be used as indices in order to select safer modification plans.

[0132] The present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the present invention being indicated by the appended claims rather than by the foregoing description, and all modification which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. 

What is claimed is:
 1. A modification risk degree measurement system for determining the degree of risk of modification in a program, comprising: an extracting module configured to extract a program constituent element from an program as an influenced element, the program constituent element being influenced by program modification data; an influenced element storage unit configured to store the influenced element; an influence range specifying module configured to specify an influence range from the influenced element; an influence range storage unit configured to store the influence range; an influence degree determining module configured to determine a degree of influence on the program by the influenced element; an influence degree storage unit configured to store the degree of influence; and a risk degree calculating module configured to calculate a modification risk degree of the program by using the influence range and the degree of influence.
 2. The modification risk degree measurement system of claim 1, wherein the influence range is determined by at least one of method units, class units, block units and variable units in the program.
 3. The modification risk degree measurement system of claim 1, wherein the influence degree is determined by at least one of value counting external variables, arguments, class variables and return values in the program.
 4. The modification risk degree measurement system according to claim 1, wherein the risk degree calculating module includes: a risk degree calculating unit to calculate the risk degree by using any of numerical values and normal values of the degree of influence and the influence range; and a risk degree display unit configured to display the risk degree two-dimensionally with the degree of influence and the influence range as parameters.
 5. The modification risk degree measurement system according to claim 1, wherein the influence degree includes: dynamic information that includes frequency of occurrence of the influenced element and execution of an operation profile. static information that includes frequency of occurrence of the influenced element as references in the program and a mutual dependency relationship between the influenced element and other elements.
 6. A program reconstruction support system for assistance to form a plan for program modifies, comprising: an extracting module configured to extract a program constituent element from an program as an influenced element, the program constituent element being influenced by program modification data; an influenced element storage unit configured to store the influenced element; an influence range specifying module configured to specify an influence range from the influenced element; an influence range storage unit configured to store the influence range; an influence degree determining module configured to determine a degree of influence on the program by the influenced element; an influence degree storage unit configured to store the degree of influence; a risk degree calculating module configured to calculate a modification risk degree of the program by using the influence range and the degree of influence; and a refactoring module configured to assist to refactor a plan for program modification by using information which includes risk degree.
 7. A method for measuring a modification risk degree of computer programs, comprising: extracting a program constituent element from a program as an influenced element, the program constituent element being influenced by program modification data; storing the influenced element; specifying an influence range from the influenced element; storing the influence range; determining a degree of influence on the program by the influenced element; storing the degree of influence; and calculating a modification risk degree of the program caused by the program modification data, by using the influence range and the influence degree.
 8. The method of claim 7, further comprising determining the influence range from at least one of method units, class units, block units and variable units in the program.
 9. The method of claim 7, further comprising determining the influence degree from at least one of value counting external variables, arguments, class variables and return values in the program.
 10. The method of claim 7, wherein calculating the modification risk degree includes: computing the risk degree by using any of numerical values and normal values of the degree of influence and the influence range; and displaying the risk degree two-dimensionally with the degree of influence and the influence range as parameters.
 11. The method of claim 7, wherein determining the degree of influence includes: deciding dynamic information that includes frequency of occurrence of the influenced element and execution of an operation profile. deciding static information that includes frequency of occurrence of the influenced element as references in the program and a mutual dependency relationship between the influenced element and other elements.
 12. A method for supporting computer program reconstruction, comprising: extracting a program constituent element from a program as an influenced element, the program constituent element being influenced by program modification data; storing the influenced element; specifying an influence range from the influenced element; storing the influence range; determining a degree of influence on the program by the influenced element; storing the degree of influence; and calculating a modification risk degree of the program caused by the program modification data, by using the influence range and the influence degree. assisting for refactoring a plan for program modification by using information which includes risk degree.
 13. A computer program product in a computer memory for determining the degree of risk of modification in a program, comprising: instructions for extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; instructions for storing the influenced element; instructions for specifying an influence range from the influenced element; instructions for storing the influence range; instructions for determining a degree of influence on the program by the influenced element; instructions for storing the degree of influence; and instructions for calculating a modification risk degree of the program caused by the program modification data by using the influence range and the influence degree.
 14. The computer program product of claim 13, wherein the instructions for determining the influence range is derived from at least one of the method units, class units, block units and variable units in the program.
 15. The computer program product of claim 13, wherein the instructions for determining the influence degree is derived from at least one of the value counting external variables, arguments, class variables and return values in the program.
 16. The computer program product of claim 13, wherein the instructions for calculating the modification risk degree of the program includes: instructions for computing the risk degree by using any of numerical values and normal values of the degree of influence and the influence range; and instructions for displaying the risk degree two-dimensionally with the degree of influence and the influence range as parameters.
 17. The computer program product of claim 13, wherein the instructions for determining the degree of influence includes: instructions for deciding dynamic information that includes frequency of occurrence of the influenced element and execution of an operation profile. instructions for deciding static information that includes frequency of occurrence of the influenced element as references in the program and a mutual dependency relationship between the influenced element and other elements.
 18. A computer program product for supporting computer program reconstruction, comprising: instructions for extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; instructions for storing the influenced element; instructions for specifying an influence range from the influenced element; instructions for storing the influence range; instructions for determining a degree of influence on the program by the influenced element; instructions for storing the degree of influence; instructions for calculating a modification risk degree of the program caused by the program modification data by using the influence range and the influence degree; and instructions for assisting to refactor a plan for program modification by using information which includes risk degree.
 19. A computer readable medium configured to store a program for measuring modification risk degree of computer programs, the program comprising: instructions for extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; instructions for storing the influenced element; instructions for specifying an influence range from the influenced element; instructions for storing the influence range; instructions for determining a degree of influence on the program by the influenced element; instructions for storing the degree of influence; and instructions for calculating a modification risk degree of the program caused by the program modification data by using the influence range and the influence degree.
 20. A computer readable medium for supporting computer program reconstruction, comprising: instructions for extracting a program constituent element from a program as influenced element, the program constituent element being influenced by program modification data; instructions for storing the influenced element; instructions for specifying an influence range from the influenced element; instructions for storing the influence range; instructions for determining a degree of influence on the program by the influenced element; instructions for storing the degree of influence; instructions for calculating a modification risk degree of the program caused by the program modification data by using the influence range and the influence degree; and instructions for assisting to refactor a plan for program modification by using information which includes risk degree. 